Thanks for the PR!

do you know what config does the action use by default? For some reason I'm not able to configure commitlint locally - I wanted to pipe a couple of commit messages through the linter so see what would get flagged.

@jhrozek, thanks for taking a look. I've tested several cases, and it looks like the default follows Minder's guidelines and should allow setting up semantic release.

I am not 100% sure but I think that this is the default config.

To test it, please open as many PRs as you want on my fork, and you'll see the errors: There are some example PRs open.

If there is any rule that needs to change, we can create a config for it or base it on the other config examples in the commitlint repo.

Ignore my last comment, I don't know why I thought that Minders guidelines were asking for semantic release commit messages, when they don't 🤦

I'll update this PR with a config that follows Chris Beans recommendations tomorrow 🙏

First and most importantly - thank you for caring about commit message hygiene, it's important over the long term. About the semantic commit messages, we had different uses in our team and eventually decided to drop them and just squash all commits in a PR together.

The squashing is actually one thing which I'm wondering would trip up the rules - I'm all for blank lines after subject, limiting length and no dot in subject. But if multiple commits are squashed I wonder if they would trip up the rule that asks for explaining the why.

The other thing is the imperative tone in the subject - I think it's a great rule to follow for humans, but I see some bot messages in our commit history that would break the rule (2445449 for example).
But it seems like those can be excluded (https://stackoverflow.com/questions/60194822/how-do-you-configure-commitlint-to-ignore-certain-commit-messages-such-as-any-th)

The first one I'll test soon (I have one PR with two commits pending now), for the second one I wonder if we could remove that rule from the config and re-add it in a subsequent PR to keep your work merging fast?

I've updated it so it checks for:

✅ Separate subject from body with a blank line
✅ Limit the subject line to 50 characters
✅ Capitalize the subject line
✅ Do not end the subject line with a period
✅ Wrap the body at 72 characters

These two rules are tricky:

• Use the imperative mood in the subject line
• Use the body to explain what and why vs. how

We could create a plugin to check for the imperative mood, but for now, I suggest merging this PR to set up some initial rules. We can address the missing imperative mood rule with a dedicated plugin later.

I've also updated the commit message for this PR since it was following the wrong standards 😬 now I know better!

@jhrozek, great idea! I've just added the rule to ignore WIP messages or messages from dependabot.

Thanks for taking the time to review this one. If this is getting more complex than it should with corner-cases like Dependabot or other services, feel free to just close it 😄

It should be ok now. Here are some tests:

Failed PR, fails:
andresgalante#9

Lint free PR, pass:
andresgalante#10

WIP PR, pass:
andresgalante#11

Dependabot PR, pass:
andresgalante#12